Integrated third-party application builder trigger for message flow

ABSTRACT

A message management platform may receive, from an application operator, a configuration of a message flow. The message flow includes one or more messages associated with trigger conditions. The platform may receive, from a code snippet incorporated in an application of a user computing device, a notification that the user computing device has used the application. The platform may associate a user identifier with the user computing device. The platform may subscribe to, on behalf of the application operator, one or more API notification channels of the application builder platform. The platform may receive an API notification from the application builder platform. The platform may determine that the application builder platform&#39;s user is associated with the user identifier used by the message management platform. The platform may determine that the event described in the payload matches the trigger condition and transmit the first message to the user computing device.

TECHNICAL FIELD

The present disclosure generally relates to a server that distributes messages to recipients on behalf of application operators and, more specifically, configuration of trigger conditions for receiving application programming interface notification from the application building platform.

BACKGROUND

Network communications to a mass audience can often be challenging as communications channels are often associated with their own requirements, protocols, formats and limitations. An organization often encounters technical difficulties in managing proper message transmission. In addition, identification of audience and determination of proper timing to transmit the proper communications are not a trivial task. An organization may not be equipped with the technical specialty to deliver network communications in an effective manner without the proper technical specialty. The issue could be especially challenging if messages are related to functionalities that are not operated by the organization.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an example system environment, in accordance with some embodiments.

FIG. 2A is a block diagram illustrating various components of an example application builder platform, in accordance with some embodiments.

FIG. 2B is a conceptual diagram illustrating an example payload of an API notification, such as a webhook notification, provided by the application builder platform, in accordance with some embodiments.

FIG. 3 is a block diagram illustrating various components of an example message management platform, in accordance with some embodiments.

FIGS. 4A and 4B are sequence diagrams illustrating an example series of interactions among entities of the system environment to deliver messages to users based on event trigger, in accordance with some embodiments.

FIG. 5 is a flowchart depicting an example process for transmitting, in accordance with some embodiments.

FIG. 6 is a block diagram illustrating an example flow plan hierarchy that may be used with the message management platform, in accordance with some embodiments.

FIG. 7 is a flowchart depicting an example process for a message management platform to provide an interface for an application operator to compose and launch a flow plan, in accordance with some embodiments.

FIG. 8A through FIG. 8F are example illustrations of graphical user interfaces provided by a message management platform for an application operator to compose a flow plan, in accordance with some embodiments.

FIG. 9 is an example of a webpage associated with an application operator where end user activity may cause detection of a trigger condition associated with a flow plan, in accordance with some embodiments.

FIG. 10 is a block diagram illustrating components of an example computing machine, in accordance with some embodiments.

The figures depict various embodiments for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles described herein.

DETAILED DESCRIPTION

The figures and the following description relate to preferred embodiments by way of illustration only. It should be noted that from the following discussion, alternative embodiments of the structures and methods disclosed herein will be readily recognized as viable alternatives that may be employed without departing from the principles of what is claimed.

Reference will now be made in detail to several embodiments, examples of which are illustrated in the accompanying figures. It is noted that wherever practicable similar or like reference numbers may be used in the figures and may indicate similar or like functionality. The figures depict embodiments of the disclosed system (or method) for purposes of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles described herein.

Configuration Overview

Disclosed embodiments herein are related to a message management platform that allows application operators to build message flow plans (e.g., message campaigns and message automation). Messages (e.g., SMS messages) based on the message flow plans are transmitted to user computing devices of end users (e.g., subscribers) who have opted-in to receive messages from specific application operators (or from specific flow plans of the specific publishers). An application operator may utilize a flow builder of the platform to create and launch one or more message flow plans for carrying out different message series for different end users to the message flow plan based on trigger conditions of the message flow plan.

The application operator may set as a message trigger condition for an initial message to be transmitted under a flow plan, target recipient criteria for selecting a group of end users from among all of the end users to the application operator who are to receive messages under the message flow plan. The message management platform may then automatically identify and transmit the initial message based on the target recipient criteria for the message flow plan to the target group of end users. The application operator may further set exclusion trigger conditions for the message flow plan based on which an end user may be temporarily excluded or permanently removed from the group of end users and thereby preventing a further message from being sent to the end user under the message flow plan. The message management platform may automatically identify and stop the transmission of messages to the end user when the exclusion trigger condition is detected with respect to the end user. The application operator may also configure the message flow plan to have different message series (e.g., different branches) by setting different trigger conditions (e.g., event-based triggers, publisher-configured triggers). The message management platform may thus automatically identify and transmit the different message series (each including one or more messages) to the different end users of the group based on the trigger conditions of the message flow plan.

Example System Environment

Referring now to FIG. 1 , shown is a block diagram illustrating an embodiment of an example system environment 100 for distributing messages based on various triggers, in accordance with some embodiments. By way of example, the system environment 100 includes a message management platform 110, application operators 120, an application builder platform 130, user computing devices 140, and a transaction fulfillment operator 150. The user computing devices 140 may be collectively referred to by the reference number 140 or individually as 140A, 140B, . . . , 140N (N being an nth device, n being some number). The entities and components in the system environment 100 may communicate with each other through networks 160.

In various embodiments, the system environment 100 may include fewer or additional components. The system environment 100 also may include different components. Also, while some of the components in the system environment 100 may sometimes be described in a singular form, the system environment 100 may include one or more of each of the components. For example, there may be multiple application operators 120 and multiple user computing devices 140. Various application operators 120 may be independent entities such as different enterprise customers of the message management platform 110, which serves as a service provider that manages the message distribution and associated actions on behalf of the application operators 120. Also, while the terms such as “server” and “operator” is used in the singular form, those terms may each include multiple instances that cooperatively or collectively perform certain functions or processes described in this disclosure. For example, a “server” may include a group of servers that are operated under a single entity or multiple entities under contract to provide various services. Each server in the group may perform a different function.

In the system environment 100, various components may be operated by the same organization or different organizations. For example, in some embodiments, the message management platform 110, the application operator 120, the application builder platform 130, and the channel 150 are each operated by a different business. In some embodiments, two or more components may be operated by the same organization. For example, the organization that controls the application builder platform 130 may also be the transaction fulfillment operator 150.

The message management platform 110 may include one or more computing servers that perform various tasks related to managing communication elements (messages, data payloads, and other forms of communications) on behalf of application operators 120. The message management platform 110 may refer to the party that operates the message management platform 110. The communication managing tasks may include providing a frontend software platform (e.g., a message flow builder in the form of a software-as-a-service SaaS platform), transmitting communication elements to various user computing devices 140 on behalf of the different application operators 120, determining conditions and target audience to transmit those communications, transmitting a series of messages based on triggered conditions, receiving responses from user computing devices 140, forwarding the responses to the application operators 120, and/or taking actions on behalf of the application operators 120.

U.S. Patent Application Publication No. 2022/0198431, entitled “Text Messaging Service Based Commerce System,” published on Jun. 23, 2022, is incorporated herein by reference for all purposes.

The messages managed and distributed by the message management platform 110 may include different types of messages such as text messaging services (e.g., short message service (SMS), multimedia messaging service (MMS)), emails (e.g., mobile emails, plain text emails, browser emails), push notification protocols (e.g., APPLE push notification, ANDROID push notification), instant messaging applications (WHATSAPP, WECHAT, TELEGRAM), in-application messages (e.g., messages sent within a mobile application), social networking systems (e.g., FACEBOOK, TWITTER), RSS feeds, web browser notifications, other suitable protocols such as simply message payloads sent as an Internet packet or a series of packets. In some embodiments, the message management platform 110 may focus on a single type of message such as a text messaging service (SMS and MMS).

By way of example, the message management platform 110 may provide a platform for an application operator 120 to design and configure an automated SMS message flow. According to the message flow, the message management platform 110 may send one or more SMS messages on behalf of the application operator 120 to a user computing device 140 based on various triggers that may be related to time, event, transaction, sequence, and/or response. The message management platform 110 may receive SMS messages from the user computing device 140 and may forward SMS messages to the application operator 120. In some embodiments, the message management platform 110 may provide a platform that connects the application operator 120 and the user computing device 140 to allow the two parties to communicate via SMS in real time. While SMS messaging may be used as the primary example throughout this disclosure, various features described may be expanded to other types of communications.

The message management platform 110 may be operated by an entity that uses a combination of hardware and software to build and operate the platform. A computing server used by the message management platform 110 may include some or all example components of a computing machine described in FIG. 10 . The message management platform 110 may sometimes be referred to as a messaging platform or simply a computing server. The message management platform 110 may include a computing server that takes different forms. In some embodiments, the message management platform 110 may be a server computer that executes code instructions to perform various processes described herein. In some embodiments, the message management platform 110 may be a pool of computing devices that may be located at the same geographical location (e.g., a server room) or be distributed geographically (e.g., clouding computing, distributed computing, or in a virtual server network). In some embodiments, the message management platform 110 may be a collection of servers that cooperatively provide messaging services as described. The message management platform 110 may also include one or more virtualization instances such as a container, a virtual machine, a virtual private server, a virtual kernel, or another suitable virtualization instance. The message management platform 110 may provide application operators 120 with various message management services and merchant services as a form of cloud-based software, such as software as a service (SaaS), through the network 160. Examples of components and functionalities of the message management platform 110 are discussed in further detail below with reference to FIG. 3 .

Application operators 120 are entities that control software applications 142 that are used by user computing devices 140. For example, an application operator 120 can be an application publisher that publishes mobile applications available through application stores (e.g., APPLE APP STORE, ANDROID STORE). In some cases, the application may take the form of a website and the application operator 120 is the website owner. In some embodiments, the application operators 120 are businesses that provide goods and/or services to end users who possess the user computing devices 140. In some embodiments, an application operator 120 sells products through an application 142 and may be referred to as a merchant. In the system environment 100, the application operators 120 may be the customers of the message management platform 110 and the customers of the application builder platform 130.

An application operator 120 may interact directly with its customers or end users in certain aspects, and may delegate certain operations, such as sending messages, to the message management platform 110. An application operator 120 may maintain accounts of its users and manage day-to-day interactions with the users while directing the message management platform 110 to distribute messages to the users on behalf of the application operator 120. For example, the application operator 120 may use a platform provided by the message management platform 110 to design messages and set conditions, branches, and intended recipients of the messages. The application operator 120, through the message management platform 110, may launch a message flow that includes a series of messages to be automatically delivered to various user computing devices 140.

By way of example, an application operator 120 may be a retail business that operates an electronic retail platform in an application 142 and uses the service of the message management platform 110 to communicate order and shipment information to various user computing devices 140. In another example, another retail business may use the message management platform 110 to transmit marketing and promotional communications (e.g., advertisements, gift cards, coupons, store credits, and receipts) in various forms of messages to user computing devices 140. In yet another example, an application operator 120 may be a retail company that hires the message management platform 110 to send SMS offers to its customers and the customers may make a purchase by directly responding to the SMS message. These are non-exhaustive examples of application operators 120. Various application operators 120 may be independent and unrelated entities, such as different unrelated businesses.

In some embodiments, a message may be considered to be transmitted from the application operator 120 regardless of whether the message publisher's server directly sends the message or the message management platform 110 sends the message.

An application builder platform 130 may include one or more computing servers that perform various tasks related to assisting application operators 120 to build applications 142, providing ready-to-use functionalities to those applications 142, operating a digital distribution platform that provides a selection of third-party functionalities that can be integrated into applications 142, providing back-end functionalities for applications 142, and/or performing actions such as fulfillment for transactions that are completed through applications 142. The application builder platform 130 may refer to the party that operates the application builder platform 130. By way of example, the application builder platform 130 may be an e-commerce platform, such as SHOPIFY, that allows application operators 120 to build an application 142, which may take the form of a mobile application, a website, or a software program, on the platform of the application builder platform 130. The application builder platform 130 may also be referred to as an e-commerce platform, a backend shopping cart platform, or a website builder platform. The application 142 built using the platform may automatically incorporate certain standard features provided by the application builder platform 130, such as the checkout feature, shopping cart, payment management, and inventory management features provided by the application builder platform 130. Hence, the application operator 120 may design, for example, a website using the platform and the website will automatically have e-commerce features. The application builder platform 130 may further provide a digital distribution platform on which various third-party features are distributed. In some embodiments, the message management platform 110 may upload a code snippet (e.g., in the form of an applet, a software development kit (SDK)) to the digital distribution platform. An application operator 120 adding the applet to the application 142 makes the application 142 have additional features that are provided by the applet in communication with the message management platform 110.

With respect to the relationship between the application operator 120 and the application builder platform 130, while the application operator 120 is the operator of an application 142, the application operator 120 may not need to run the application in terms of the application's day-to-day software and hardware operations. The application operator 120 may control the application 142 in the business sense, such as being the owner of the application 142. For example, a retail merchant application operator 120 may own its retail website or retail mobile application. However, an application operator 120 may delegate the application's day-to-day software and hardware operations to the application builder platform 130. As such, in some embodiments, an application operator 120 may also be referred to as an application owner, an application publisher, a business, a service provider, and/or a merchant. In some embodiments, the application operator 120 may run some part of the day-to-day software and hardware operations of its application 142 while the application builder platform 130 provides support and additional features (e.g., e-commerce capability, backend, and platform) to the application 142.

The application builder platform 130 may be operated by an entity that uses a combination of hardware and software to build and operate the platform. The application builder platform 130 may include some or all example components of a computing machine described in FIG. 10 . The application builder platform 130 may sometimes be referred to as a website builder server, an e-commerce platform, an online-store building platform, or simply a computing server. The application builder platform 130 may include a computing server that takes different forms. In some embodiments, the application builder platform 130 may be a server computer that executes code instructions to perform various processes described herein. In some embodiments, the application builder platform 130 may be a pool of computing devices that may be located at the same geographical location (e.g., a server room) or be distributed geographically (e.g., clouding computing, distributed computing, or in a virtual server network). In some embodiments, the application builder platform 130 may be a collection of servers. The application builder platform 130 may also include one or more virtualization instances such as a container, a virtual machine, a virtual private server, a virtual kernel, or another suitable virtualization instance. Examples of components and functionalities of the application builder platform 130 are discussed in further detail below with reference to FIG. 2A.

A user computing device 140 is a computing device that is possessed by an end user who may be a customer or a subscriber of an application operator 120. An end user may perform transactions, such as purchases, service arrangement, and communications, with the application operator 120 through the application 142 that is operated by the application operator 120 with some features that may be provided or supported by the application builder platform 130. An end user may also receive messages from the message management platform 110 that are related to an application operator 120. For example, the end user may subscribe to messages of an application operator 120 and the message management platform 110 send those messages to the end user on behalf of the application operator 120.

Examples of user computing devices 140 include personal computers (PC), desktop computers, laptop computers, tablets (e.g., iPADs), smartphones, wearable electronic devices such as smartwatches, smart home appliances (e.g., smart home hubs and controllers), vehicle computer systems, or any other suitable electronic devices. In some embodiments, for a message management platform 110 that specializes in SMS messages, user computing devices 140 may be any mobile devices (e.g., phones, tablets) that are equipped with Subscriber Identity Module (SIM) cards, electronic or physical, and/or are associated with phone numbers.

Some of the user computing devices 140 may run one or more applications 142 that are developed by various application operators 120 using the application builder platform 130. For example, the user may download various mobile apps and visit different websites that are operated by various businesses. Each instance of the mobile app and website may be an example of an application 142. Each application 142 may be developed by different creators. For example, in some embodiments, a first application 142 is developed by a first application operator 120 and a second application 142 is developed by a second application operator 120.

Various applications 142 may take different forms. For example, some applications may take the form of webpages that have backend functionalities built using JAVASCRIPT, RUBY ON RAIL, etc. Other applications may be web applications that may appear as SaaS platforms. Yet other applications may be mobile apps that may run on Swift for iOS and other APPLE operating systems or on Java or another suitable language for ANDROID systems. In another case, an application 142 may be a software program that operates on a desktop computer that runs on an operating system such as LINUX, MICROSOFT WINDOWS, MAC OS, or CHROME OS.

An application 142 may incorporate a code snippet 144 that is provided by the message management platform 110 to enable the application 142 to include functionalities provided by the message management platform 110. In some embodiments, the incorporation may be performed through the digital distribution platform provided by the application builder platform 130. An application operator 120 may select the code snippet 144 of the message management platform 110 from a list of applets at the marketplace of the digital distribution platform and the application builder platform 130 in turn provides or causes a server of the message management platform 110 to provide the code snippet 144 as part of the code of the application 142. In some embodiments, the code snippet 144 may also be incorporated at the code level. This may be done by importing one or more libraries of functions and codes of the code snippet 144 to the software code of the application 142 in the header section of the software code and having the code calling one or more functions of the code snippet 144.

While the application operator 120 primarily operates the application 142, the code snippet 144 allows the application 142 to communicate with the message management platform 110. For example, an application operator 120 may be a retail business that develops an application 142 for its customers to purchase items through the application 142. A customer may opt-in to allow the application 142 to track certain analytics, actions, browsing history, and/communications occurred associated with the application 142. The information may be captured by the code snippet 144 and forwarded to the message management platform 110. In another example, the code snippet 144 may be in communication with the message management platform 110 that generates user-tailored information (e.g., personal information, custom promotional messages) to display the information in the application 142, such as in the form of a pop-up, side panel, embedded content, or another suitable way of presentation. In various embodiments, the code snippet 144 may perform any suitable tasks, from front end features, such as providing a control element that is operated by the message management platform 110 on the frontend, to any backend functionalities.

Multiple instances of the code snippet 144 developed by the message management platform 110 may be included in different applications 142. For example, different application operators 120 may be customers of the message management platform 110 and include the code snippet 144 in the applications 142, as illustrated in the user computing device A 140A. Those applications 142 that incorporate the same type of code snippet 144 have included similar functionalities and services provided by the message management platform 110.

Some of the user computing devices 140 may store a cookie 146 that is issued by the message management platform 110. The cookie 146 is used to serve as an identifier so that the message management platform 110 may track a particular user computing device 140 and associate the instance(s) of code snippet 144 that are used in the user computing device 140 with a particular end user or a particular phone number.

The transaction fulfillment operator 150 may be an entity that completes a transaction between an end user and an application operator 120. For example, an end user may make a purchase through the application 142 which is supported by the e-commerce backend provided by the application builder platform 130. After the confirmation of the purchase, the application builder platform 130 (or the application operator 120) may transmit the detail to the transaction fulfillment operator 150 to carry out the transaction, which may include packaging and shipment. The transaction fulfillment operator 150 may provide notifications to the application builder platform 130 regarding various stages of status updates of the purchase, such as the shipment of the parcel, the delivery of the parcel, etc.

The networks 160 provide connections to the components of the system environment 100 through one or more sub-networks, which may include any combination of the local area and/or wide area networks, using both wired and/or wireless communication systems. In some embodiments, the networks 160 use standard communications technologies and/or protocols. For example, a network 160 may include communication links using technologies such as Ethernet, 802.11, worldwide interoperability for microwave access (WiMAX), 3G, 4G, Long Term Evolution (LTE), 5G, code division multiple access (CDMA), digital subscriber line (DSL), etc. Examples of network protocols used for communicating via the network 160 include multiprotocol label switching (MPLS), transmission control protocol/Internet protocol (TCP/IP), hypertext transport protocol (HTTP), simple mail transfer protocol (SMTP), and file transfer protocol (FTP). Data exchanged over a network 160 may be represented using any suitable format, such as hypertext markup language (HTML), extensible markup language (XML), JavaScript object notation (JSON), structured query language (SQL). In some embodiments, all or some of the communication links of a network 160 may be encrypted using any suitable technique or techniques such as secure sockets layer (SSL), transport layer security (TLS), virtual private networks (VPNs), Internet Protocol security (IPsec), etc. The networks 160 also include links and packet switching networks such as the Internet.

Example Application Builder Platform Components

FIG. 2A is a block diagram illustrating various components of an example application builder platform 130, in accordance with some embodiments. An application builder platform 130 may include an application building platform 205, an order and inventory backend 210, a digital distribution platform 215, a notification subscription engine 220, and an application programming interface 225. In various embodiments, the application builder platform 130 may include fewer or additional components. The application builder platform 130 also may include different components. The functions of various components in application builder platform 130 may be distributed in a different manner than described below. Moreover, while each of the components in FIG. 2A may be described in a singular form, the components may present in plurality.

The application building platform 205 may take the form of a front-end software platform that allows an application operator 120 to design and configure various visual elements and functionalities of an application 142. The building of an application 142 may be based on standard language such as HTML, CSS, JAVASCRIPT, etc. The application builder platform 130 may provide certain pre-built features that allow the application operator 120 to incorporate into the application 142. The pre-built features may include an e-commerce platform, shopping cart features and related order and inventory backend 210, a search engine for the application, payment management, and analytics. As discussed in further detail below, additional features and functionalities may be selected at the digital distribution platform 215 for applets that are provided by other parties.

The order and inventory backend 210 may be a management system that allows the application operator 120 to act as a merchant to sell various goods at the application 142 and manage the inventory of those goods. For each product for a particular merchant, the application builder platform 130 may assign a unique product identifier. In some products that have sub-variants, such as apparel that have sizes and colors, the application builder platform 130 may assign a variant identifier. The order and inventory backend 210 may also allow the application operator 120 to define a taxonomy of products that have categories, levels of sub-categories, and products. The application builder platform 130 may also assign an identifier for each category or sub-category. The application builder platform 130 may include the identifier for a page in the application 142 that is related to the product, variant, category, or subcategory. For example, on the product page of the merchant application 142 that display product detail to the customers, the URL of the page or the HTML of the page may include the product identifier.

The digital distribution platform 215 may take the form of a marketplace, which may be open or semi-open, to various third-party developers to list their software applications that can be incorporated into an application 142 of an application operator 120. An application operator 120 may browse and select various applications on the digital distribution platform 215. For the applications that are selected by the application operator 120, the code of the selected applications is incorporated into the application 142 to expand the functionalities and features of the application 142. For example, the message management platform 110 may publish the code snippet 144 in the digital distribution platform 215 and an application operator 120 may incorporate the code snippet 144 into an application 142.

The notification subscription engine 220 allows an application operator 120 to subscribe to different notification channels that are provided by the application builder platform 130. The notification channels may be divided based on event types, merchants, and other suitable factors. For example, the application builder platform 130 may manage the e-commerce and sales of products on behalf of an application operator 120. The notification channels may include purchase notifications, shipment notifications, delivery notifications, etc. An application operator 120 may select one or more channels to subscribe. In some embodiments, an application operator 120 may authorize the message management platform 110 to subscribe to one or more notification channels on behalf of the application operator 120. The subscription process may include providing a credential of the application operator 120 to the application builder platform 130 through an API call. The API call includes a parameter (“purchase” for purchase events, “shipment” for shipment events) that specifies the notification channel to subscribe. After subscription, the application builder platform 130 provides notifications of a particular type of event to the recipient (the application operator 120 or the message management platform 110).

The application programming interface 225 allows the application builder platform 130 to provide notifications for recipients on subscribed channels. In some embodiments, the notifications can be provided in the form of pull notifications by conventional API in which the recipient (the application operator 120 or the message management platform 110) may continuously poll the API. In some embodiments, the notifications can be provided through webhook, which may be a form of push API notifications where the application builder platform 130 automatically transmit the API notifications to the recipient when a matching event has occurred. An API notification, such as a webhook notification, may include a header and a payload. The payload may be in the format of key-value pairs that are in the format of JSON, XML, YAML, CSV, or another suitable format.

FIG. 2B is a conceptual diagram illustrating an example payload 250 of an API notification, such as a webhook notification, provided by the application builder platform 130, in accordance with some embodiments. The payload 250 may take the form of key-value pairs. The keys and values shown in the payload 250 are for example only. In various embodiments, the payload 250 may include fewer, additional, or different keys. In some embodiments, the pairs may be nested.

The top portion of the example payload 250 may be the first level of key-value pairs and may be referred to as the wrapper 260. The wrapper 260 includes the body 270 of the payload 250 and other high-level information of the payload 250, such as the identifier of the API notification, the identifier of the order related to this notification, the subscription channel 262 of the notification (e.g., “subject_type”: “Shipment”) and other information. The body 270 may be another nested key-value pairs that include additional information contained in the API notification. An example body 270 is separately shown in the lower portion of FIG. 2B.

The body 270 may take the form of another layer of nested key-value pairs that include various information regarding the order, the end user, and other related identification information. In some embodiments, the body 270 may include a key for the identifier 272 of an application 142 and an IP address 274 of the user computing device 140 engaging in the transaction. The application builder platform 130 may also have the information of the end user, which is recorded in the key “customer.” The information of the end user may include a unique user identifier 282, the email address 284 of the end user, and the phone number 286 of the end user. The body may further include a key for the order 292 and the value corresponding to the order 292 may include detailed information about the order 292. In some embodiments, the API notification may include an array that lists all of the items 294 in the order 292. The items 294 may be in the format of an array that includes the product or variant identifier of those items in the order 292.

Example Message Management Platform Components

FIG. 3 is a block diagram illustrating various components of an example message management platform 110, in accordance with some embodiments. A message management platform 110 may include the application operator management engine 305, a message recipient management engine 310, an API subscription and data engine 315, a code snippet management engine 320, a cookie management engine 325, a message flow building platform 330, an event management engine 335, a message flow management engine 340, and an instant messaging platform. In various embodiments, the message management platform 110 may include fewer or additional components. The message management platform 110 also may include different components. The functions of various components in message management platform 110 may be distributed in a different manner than described below. Moreover, while each of the components in FIG. 3 may be described in a singular form, the components may present in plurality.

The components of the message management platform 110 may be embodied as software engines that include code (e.g., program code comprised of instructions, machine code, etc.) that is stored on an electronic medium (e.g., memory and/or disk) and executable by a processing system (e.g., one or more processors and/or controllers). The components also could be embodied in hardware, e.g., field-programmable gate arrays (FPGAs) and/or application-specific integrated circuits (ASICs), that may include circuits alone or circuits in combination with firmware and/or software. Each component in FIG. 3 may be a combination of software code instructions and hardware such as one or more processors that execute the code instructions to perform various processes. Each component in FIG. 3 may include all or part of the example structure and configuration of the computing machine described in FIG. 10 .

The application operator management engine 305 manages the profiles and credentials of application operators 120 and stores saved message flow templates for retrieval by the application operators 120. For example, an application operator 120 that intends to use the message publisher management engine 305 to launch a message flow to distribute messages to various end users may create an account with the message management platform 110. The message management platform 110 stores the customer's profile, metadata, and credential and associate the information with a unique identifier. The application operator 120 may create message templates, message flow templates, specify criteria of message distribution, and goals of message flows, select or specify types of events and analytics to be captured by the message management platform 110, manage subscription plans, and configure other settings with the message management platform 110. The templates and settings are associated with the customer identifier and can be retrieved, duplicated, edited, and deleted based on the application operator's preferences and actions entered through the message flow building platform 330 and/or API provided by the message management platform 110.

In some embodiments, the message publisher management engine 305 may also store credentials or access keys of application operators 120. The application operator 120 may provide the message management platform 110 an access key, such as an API access key with a particular level of access privilege, for the message management platform 110 to subscribe to various notification channels provided by the application builder platform 130.

The message recipient management engine 310 manages the profile of end users that receive messages from the message management platform 110. An application operator 120 may specify the intended audience based on the users' segmentation and tags that categorize the users. The message management platform 110 may associate end users based on the user computing devices 140 and/or phone numbers. An end user or the corresponding user computing device 140 may be assigned a subscriber identifier. Depending on whether a user computing device 140 is determined as possessing an application 142, a code snippet 144, and/or a cookie 146, the message recipient management engine 310 may also associate the subscriber identifier with one or more of the following: phone number, email address, device identifier, application identifier, and/or cookie identifier.

The message recipient management engine 310 may maintain tags for end users for one or more purposes such as audience segmentation. The tags may take the form of metadata tags. The tags may include information such as preferences of the user computing devices 140, opt-in or opt-out options of the user computing devices 140 (e.g., subscribed or not), and other characteristics of the message recipients, including consented information such as gender, age, interested products, interested news, etc. Based on the tags, the message recipient management engine 310 may categorize the end users into one or more groups. The message recipient management engine 310 may also store the entire records of messages and chat history of each user computing device 140, such as metadata of the messages (e.g., date and time of the messages). The message recipient management engine 310 may also store the purchases and other actions taken by the end users.

The API subscription and data engine 315 subscribes to various API notification channels (e.g., webhook channels) provided by the application builder platform 130 on behalf of application operators 120. For example, an application operator 120 authorizes the message management platform 110 to receive data form the application builder platform 130 for relevant information related to the e-commerce service of the application operator 120. In some embodiments, the API subscription and data engine 315 receives payloads 250 from the application builder platform 130 webhook.

The API subscription and data engine 315 in turn may identify the nature of each payload 250 by reviewing the notification channel type 262. Discussing FIG. 3 in conjunction with FIG. 2B, the API subscription and data engine 315 may also identify the user computing device 140 based on the application identifier 272 and device IP address 274. In some embodiments, the API subscription and data engine 315 may have a mapping of subscriber identifiers stored by message recipient management engine 310 and the user identifiers 282 used by the application builder platform 130. In such a case, the API subscription and data engine 315 may be able to immediately determine the user who is specified in payload 250. In some cases, if a particular user identifier 282 is not available in the system of message management platform 110, the API subscription and data engine 315 may inspect the email 284 and the phone number 286 to determine the user who is specified in the payload 250. The API subscription and data engine 315 may review various values in the payload 250 and in turn associate the data to user, product, and/or event records that are maintained by the message management platform 110 on behalf of one or more application operators 120.

The code snippet management engine 320 manages the code snippets 144 and receives data from the code snippets 144. In some embodiments, a version of the code snippet 144 may be a background applet that tracks users' actions in the e-commerce system provided in the application 142. For example, each product or category page of the e-commerce system may be associated with a product, variant, and/or category identifier assigned by application builder platform 130 as discussed in the order and inventory backend 210 in FIG. 2A. Those identifiers may be generally referred to as item identifiers. For an item page in the application 142, the item identifier corresponding to the item may be included in the HTML code or the URL of the item page. The code snippet 144 may parse the item identifier as the end user visits a page and transmit the item identifier to the code snippet management engine 320. As such, the code snippet 144 may be used to track various user actions including viewing a product page, adding an item to a shopping cart, beginning to check out, completing a transaction, etc. Based on preapproval by the end user, the code snippet 144 may transmit the information of the user action to the code snippet management engine 320.

Additionally, or alternatively, in some embodiments, the code snippet 144 may maintain one or more active user interface elements intended for display in the application 142, such as in the form of a popup. The code snippet 144 may receive a message from the message management platform 110 including configuration data for the message. The code snippet 144 may cause the application 142 to display the message. This may be used for in-app promotional content and personal content for the application 142.

The cookie management engine 325 installs and manages various cookies 146 in user computing devices 140. A cookie 146 may be installed on a user computing device 140 through an approval process. The approval process may vary depending on embodiments and situations. For example, the approval may take the form of an end user affirmatively selection subscription of contents from the application operator 120, via clicking a message or responding to a text message such as an SMS message. In another case, the approval may take the form of an end user authorizing the use of cookies. In some embodiments, when a user opens an application 142 that has the code snippet 144 installed, the code snippet 144 communicates to the message management platform 110 to see if there is a cookie already installed at the user computing device 140. If not, the code snippet management engine 320 may generate a random string that can be incorporated as part of the cookie 146 and send the random string to the user computing device 140. In turn, the user approves the cookie 146 and the cookie is generated and stored in the user computing device 140. The random string may be used as an identifier or a part of the identifier for a user computing device 140. In communicating with the message management platform 110, code snippet 144 may refer to one or more identifiers of the cookie 146 as an identification source for a particular user computing device 140.

The message flow building platform 330 may take the form of a front-end software application interface for application operators 120 to design and manage various messages, message flows, audience selection criteria, and message trigger conditions. Each message flow may be referred to as a message series, which includes a series of related messages that are sent to a user computing device 140 when a certain condition is met. The messages in a message flow may be linked together in any suitable ways, branched or linear, cyclic or acyclic. The triggers may be based on time, audience, events, and other suitable conditions. Examples features, functionalities, and graphical user interface elements of the message flow building platform 330 for configuring a message flow are shown in FIG. 6 through FIG. 8F.

The event management engine 335 manages and stores events associated with the users, user computing devices 140, and applications 142. The events may be transmitted directly from the user computing devices 140, the application operators 120, the code snippets 144 that are installed in user computing device 140, and API notifications, such as webhook notifications, of the application builder platform 130.

Events transmitted from the application operators 120 or third parties may trigger the transmission of one or more messages by the message management platform 110 to one or more user computing devices 140. By way of example, the message management platform 110 may receive an API notification from the application builder platform 130 that includes a customer identifier 282 in the payload 250. The event management engine 335 may match the customer identifier 282 of the application builder platform 130 to the subscriber identifier 310 to determine the end user or a particular user computing device 140 that is related to the event described in the API notification. The event management engine 335 determines the message flows that the particular user computing device 140 is currently being enrolled in and determines if the event meets any of the trigger conditions specified by the application operator 120. In response to matching the event to a trigger condition, the message management platform 110 sends a message specified in the message flow to the particular user computing device 140.

An event notification may also be transmitted from a code snippet 144 of an application 142. For example, the code snippet 144 may track the actions of the end user in browsing or purchasing on an e-commerce application 142. The code snippet 144 may transmit notifications to the message management platform 110 describing the actions taken by the user and the products that are associated with the actions. The event management engine 335 stores the events and also determines if an event matches a trigger condition in a message flow specified by the application operator 120.

Events managed by the event management engine 335 may be of any suitable nature. In some cases, the events may be related to actions taken by an end user in using an application 142. For example, the actions can be visiting a product page, subscribing to certain types of information, beginning to check out, completing a checkout, canceling a transaction, etc. The events may also be related to actions taken by a transaction fulfillment operator 150 such as completing an order, placing an order for shipment, delivery of an item, etc. Events may also be related to public events, general events, or events associated with the business of the application operator 120. For example, the events may be a flight delay, a weather issue, or a change in the business of the application operator 120. Events may further be related to the usage of an application 142 such as opening the application, closing the application, and uninstalling the application. Events may further be related to responses provided by the end user such as SMS messages sent from the user.

The message flow management engine 340 manages the message series that are designed and saved by various application operators 120. The message flow management engine 340 may cause a server to transmit various messages to different user computing devices 140 based on different conditions. A message flow may be associated with a start condition, an end condition, message recipient selection criteria, a message order, message branching, and trigger conditions and channels of communication.

A start condition may include various rules that specify when a message series will be triggered for a particular candidate user computing device 140. A trigger condition may be an event, such as a user event that is received via an API notification from the application builder platform 130 indicating the user has performed an action. For example, a message series may be triggered when a user completed a purchase. The start condition may also be manually started by an application operator 120 without a trigger condition. For example, the application operator 120 may manually select assign a message flow to an end user. This may occur anytime such as when the application operator 120 is in a chat session with the end user via the instant messaging platform 345. In some embodiments, the start condition may also be met through audience segment criteria.

A trigger condition may also be a condition that causes the message flow management engine 340 to send a message in the message flow. For example, a message series may begin N hours after a user has created an account with the application operator 120. Other trigger conditions may include tag change, location matching, location attributes, an event occurring, etc. In some cases, the message series starts immediately after a trigger condition is met. In other cases, the message series is scheduled based on the timing and date.

The start condition or trigger conditions may also include certain limitations. For example, the limitation may prevent the message management platform 110 from involving a user computing device 140 in more than a certain number of message flows within a predetermined period of time. The limitation may also prevent the message management platform 110 from involving a user computing device 140 in a repeated message journey.

An end condition may include various rules that specify when a message series is completed. An application operator 120 may specify that a message series is completed after all messages in the series are sent. Other end condition examples may specify rules for a message series to end prematurely. For example, a message series may end on a conversion event or an event transmitted via the API notification from the application builder platform 130. A conversion event is associated with a conversion condition. The message management platform 110 may exit a user computing device 140 when the conversion event is detected. For example, in a marketing campaign, when a user computing device 140 makes a purchase, the application operator 120 may specify that the marketing campaign should be ended. A cancellation event may be an event that is indicated by the user computing device 140 or the application operator 120 to stop the message series. For example, a user computing device 140 may want to opt-out or unsubscribe from the message series.

The message order and message branching allow an application operator 120 to select how the messages in a series are arranged. A message series can be linear or can be branched. The application operator 120 may also specify conditions to skip one or more messages.

The selection of messages in a message flow may further depend on the recipient's response or a lack of response. For example, the message flow may be distributed via SMS which allows the user to respond. The message management platform 110 may determine that the recipient did not provide a response to messages and select a message branch based on this condition. In another example, the user may provide a response via SMS. Based on the type of response and the goal specified by the application operator 120 when designing the message flow, the message management platform 110 may select a different subsequent message to be sent to the recipient 140.

The instant messaging platform 345 may be a front-end software platform that allows agents of message management platform 110 or an application operator 120 to communicate with users in real-time. For example, a user may be enrolled in a message flow and has received one or more messages via SMS. The user may decide to provide a response to one of the messages. In some embodiments, the instant messaging platform 345 may transition the user to an instant messaging mode in which an agent is assigned to communicate with the user. In some embodiments, a message flow may be triggered through an instant conversation between an agent and a user. The agent may enroll the user in a message flow through the instant messaging platform 345.

Example Event Trigger Message Process

FIGS. 4A and 4B are sequence diagrams illustrating an example series 400 of interactions among entities of the system environment 100 to deliver messages to users based on event trigger, in accordance with some embodiments. The series 400 illustrated in FIGS. 4A and 4B represents specific sets of instructions that may be stored in one or more computer-readable media, such as memory of different servers. The instructions, when executed by one or more processors of the depicted entities, cause one or more processors to perform the described interactions. As depicted in FIGS. 4A and 4B, the series 400 is performed by an application operator 120, the application builder platform 130, the message management platform 110, the application 142 that has incorporated the code snippet 144, and a user computing device 140. The sequence of interactions 400 depicted in FIGS. 4A and 4B is merely an example of sequence of interactions, and in other embodiments the sequence of interactions may include fewer, additional, or different actions performed by the same or different entities. While the steps in series 400 are illustrated graphically in FIGS. 4A and 4B as sequences of steps, some of the steps may occur in different sequences than illustrated or may occur concurrently with other steps. Also, while series 400 is depicted as a single series, in various embodiments and situations the series 400 may be further broken down into multiple series 400. For example, the series depicted in FIG. 4A and the series depicted in FIG. 4B may be two independent series.

In the series 400, an application operator 120 may configure 402 an application 142 at the application builder platform 130, such as using the application building platform 205. The design and configuration of the application 142 may include writing backend code using language such as JAVASCRIPT, RUBY ON RAIL, PYTHON, etc., designing front-end elements and pages using HTML and CSS, and incorporating standard features provided by the application builder platform 130 such as the e-commerce functionality and order and inventory backend. The application builder platform 130 may enable 404 the order and inventory backend 210 for the application 142 published by the application operator 120.

The application operator 120 may incorporate additional features to the application 142. For example, the application builder platform 130 may provide 406 a list of applets at the digital distribution platform 215 for the application operator 120 to select and add. In some embodiments, the application operator 120 may select 408 the code snippet 144 published by the message management platform 110. In response, the application builder platform 130 may install 412 the code snippet 144 in the application 142 by incorporating the code of the code snippet 144 into the code of the application 142.

By selecting the code snippet 144 at the digital distribution platform 215, the message management platform 110 may request 414 the application operator 120 to provide authorization and delegation on certain features and privileges that are possessed by the application operator 120. For example, the application operator 120 may provide 416 authorization to allow code snippet 144 to track user actions on the application 142 and provide 416 delegation for the distribution of messages to end users to the message management platform 110. The application operator 120 may also provide authorization and credentials to the message management platform 110 for the message management platform 110 to subscribe to one or more API notification channels provided by the application builder platform 130.

An end user, through his/her user computing device 140, may request 418 for the application 142. The request may take different forms and may be directed to the application operator 120 and/or the application builder platform 130. For example, if the application 142 takes the form of a website, the request may simply be downloading the website. The download request may be directed to the application operator 120 or the application builder platform 130, depending on which party hosts the website. In some embodiments, the application 142 may take the form of a mobile app. In such a case, the request may be an installation request through an app store. Regardless of the form of the application 142, the user computing device 140 may download 420 the application 142.

Upon the user's usage 422 of the application 142, the code snippet 144 may determine 428 that there is no cookie issued by the message management platform 110 stored in the user computing device 140. In turn, the code snippet 144 may notify 426 the message management platform 110 that the application 142 is in the first time use of the user computing device 140. The message management platform 110 may generate a random string that may serve as the subscriber identifier or part of the subscriber identifier used in the cookie. The message management platform 110 may transmit 428 the cookie to the user computing device 140. The user, who controls the user computing device 140, may choose to accept 430 the cookie. The series 400 depicted in FIG. 4A is completed and message management platform 110 may now be authorized to track the user's actions using the code snippet 144.

Referring now to FIG. 4B, the application operator 120 may configure 442 a message flow that includes a series of messages, whether the message flow is branched or linear, cyclic or acyclic, individually targeted or campaign based that targets more than one users. The application operator 120 may also set trigger conditions for sending one or more messages. For example, some of the trigger conditions may be event-based. The message management platform 110 in turn may store 444 the message flow and select the target audience.

Meanwhile, the message management platform 110 may subscribe 446 to one or more API notification channels of the application builder platform 130 on behalf of the application operator 120. The subscription step 446 may occur anytime after the application operator 120 provides authorization in step 416.

The message management platform 110 may determine that a particular user who is associated with one of the user computing devices 140 is an intended audience of the message flow. The transmission of a message may be triggered based on various conditions and the series 400 provides some non-limiting examples. In some embodiments, the message management platform 110 may transmit 448 an initial message to the user computing device 140 upon determining the user is an intended audience. In some cases, a message may be triggered from a notification of the code snippet 144. In other cases, a message may be triggered from an API notification sent from the application builder platform 130. Other message triggers may include time triggers, other action triggers, automatic triggers, or any suitable triggers. Those other triggers are not illustrated in FIG. 4B.

One of the triggers may be based on a notification from the code snippet 144. By way of example, the user computing device 140 may issue 452 a browsing action. In turn, the application 142 may pull 454 information from the application builder platform 130 that hosts the pages of the application 142. The application builder platform 130 may transmit 456 HMTL files and other packages to the application 142 for the application 142 to display a page. The page may be an item page. The application builder platform 130 may include an item identifier in the URL of the item page or inside the HTML file. The code snippet 144 may determine 458 the nature of the action of the end user and the item identifier associated with the item page. For example, the nature of the action may be simply browsing, bookmarking an item, adding an item to the cart, etc. The code snippet 144 may transmit 462 a notification to the message management platform 110 that includes the nature of the action, metadata related to the action (e.g., time duration of browsing), and the item identifier. Based on the received information, the message management platform 110 may determine 464 that the nature of the action matches a trigger condition in the message flow for sending one of the messages. In turn, the message management platform 110 may transmit 466 a first trigger-based message to the user computing device 140.

Another example trigger may be based on an API notification from the application builder platform 130. The user computing device 140 may issue a transaction action to the application 142. For example, the transaction action may be purchasing an item, requesting a shipment, etc. The application 142 may use the order and inventory backend 210 provided by the application builder platform 130 in fulfilling any purchase request. The application 142 may transmit 474 the transaction request to the application builder platform 130. The application builder platform 130 may in turn carry out 476 the transaction such as by completing the order, initiating a shipment, etc. Based on the nature of the actions performed by the application builder platform 130, the application builder platform 130 may transmit 478 one or more API notifications to the message management platform 110, which has subscribed to the API notification channels. The message management platform 110 may use the API subscription and data engine 315 and the event management engine 335 to parse the data in an API notification. In turn, the message management platform 110 may determine 482 that the nature of the action recorded in the API notification may match one of the trigger conditions. The message management platform 110 may transmit a second trigger-based message to the user computing device 140.

While step 472 through step 484 are illustrated as subsequent steps of the step 452 through step 466, an API notification-based trigger may occur before or concurrently with a code snippet-based trigger. Also, the initial message may also be triggered based on a code snippet notification or an API notification.

While the series 400 illustrates that the triggers are used to cause the message management platform 110 to transmit a message, in some situations a trigger may also cause the message management platform 110 to stop sending messages to a user computing device 140 or to terminate a message flow. Those triggers may also be based on time, code snippet notification, API notification, etc. The series of terminating a message flow based on a trigger is similar to the series 400 except the transmission 484 is changed to a termination step. Detail of the series for terminating a message flow is not further illustrated.

Example Message Transmission Process

FIG. 5 is a flowchart depicting an example process 500 for transmitting one or more trigger-based messages, in accordance with some embodiments. The process 500 may be performed by one or more servers of the message management platform 110. The process 500 may be embodied as a software algorithm that may be stored as computer instructions that are executable by one or more processors. The instructions, when executed by the processors, cause the processors to perform various steps in the process 500. In various embodiments, the process 500 may include additional, fewer, or different steps.

In some embodiments, the message management platform 110 may receive 510, from an application operator 120, a configuration of a message flow. The message flow includes one or more messages. For example, a first message in the message flow may associated with a trigger condition. The graphical user interface (GUI) is part of a message flow builder that allows the application operator to build the message flow. Examples of GUI are illustrated in FIG. 8A through 8F.

In this disclosure and claims, the phrases “first message” and “second message” are merely identifiers to distinguish two different messages. The use of “first,” “second,” “third,” does not imply that the “first message” has to be the start message of the entire message flow or that “first,” “second,” “third” have an order, sequence, or consecutiveness. For example, the second message may be a preceding messaging than the first message and there can be multiple messages between the first and second messages.

In some embodiments, the message management platform 110 may receive 520, from a code snippet 144 incorporated in an application 142 of a user computing device 140, a notification that the user computing device 140 has used the application 142. For example, this might be the first the user visits a website or open a mobile application. In some embodiments, the application 142 may be controlled by the application operator 120 and has a backend component that is operated by an application builder platform 130. The code snippet 144 is listed in a digital distribution platform 215 the application builder platform 130. The code snippet 144 may check if a cookie 146 of the message management platform 110 exists in the user computing device 140. If not, the code snippet 144 may notify the message management platform 110 to generate a cookie 146. For example, the message management platform 110 may generate, responsive to receiving, from the code snippet, the notification that the user computing device has used the application, a random string that is used as at least a part of the user identifier. The message management platform 110 may generate a cookie 146 based on a random string. The message management platform 110 may transmit the cookie 146 to the user computing device 140. The user computing device 140 may store the cookie 146 that is used by the message management platform 110 to track the user computing device 140. In some embodiments, the message management platform 110 may associate 530 a user identifier with the user computing device. The user identifier may be based on the random string of the cookie 146.

In some embodiments, the message management platform 110 may subscribe to 540, on behalf of the application operator 120, one or more API notification channels of the application builder platform 130. Event natures corresponding to the one or more API notification channels are selectable in the graphical user interface as candidate trigger conditions. For example, the API notification channels that are available to subscribe may be put in a list at the message flow building platform 330 as selectable candidate trigger conditions.

In some embodiments, the message management platform 110 may identify 550 the user computing device 140 as an intended recipient of the message flow. The identification may be based on user specific actions, user browsing history, and/or user tags that are discussed in further detail in FIG. 6 through FIG. 8F. For example, the message flow may be a series of automated messages that are to be sent to provide information on an order after a user completes an order. The user computing device 140 may be selected based on the user completing an order. In another situation, the message flow may be a message campaign that is to be distributed to a number of end user subscribers. The user computing device 140 may be selected based on user tags that identify characteristics of the users.

In some embodiments, the message management platform 110 may receive 560 an API notification from the application builder platform 130. The API notification may include a payload 250 that includes information describing an event associated with a user of the application builder platform 130. The API notification is a webhook notification. The payload comprises a plurality of key-value pairs, the plurality of key-value pairs comprise a second user identifier used by the application builder platform 130 and a phone number of the user of the application builder platform 130. The event associated with the user of the application builder platform 130 may be related to a transaction performed at the backend component that is operated by the application builder platform 130. For example, the backend component may be the order and inventory backend 210 or other examples that are discussed in this disclosures.

In some embodiments, the message management platform 110 may determine 570 that the user of the application builder platform 130 is associated with the user identifier used by the message management platform. For example, the payload 250 has a customer identifier 282, email address 284, or phone number 286 that can be matched to the database maintained by the message management platform 110 to establish the association.

In some embodiments, the message management platform 110 may determine 580 that the event described in the payload matches the trigger condition. For example, the payload 250 may include subject type 262 and/or order information 292 that may be used by the message management platform 110 to determine the nature of the user action performed. After the nature is determined, the message management platform 110 may determine whether the nature match a trigger condition in the message flow. In some embodiments, the message management platform 110 may transmit 590 the first message to the user computing device.

In some embodiments, the message management platform 110 may receive a second notification from the code snippet related to a browsing event of the user computing device, wherein the code snippet has determined an item identifier from a webpage associated with the browsing event. The message management platform 110 may determine that the browsing event meets a second trigger condition associated with a second message in the message flow. The message management platform 110 may transmit the second message to the user computing device.

Example Flow Plan Hierarchy

FIG. 6 is a block diagram illustrating an example flow plan hierarchy that may be used with the message management platform 110, in accordance with some embodiments. The message flow plan 600 may include steps 610 that are connected to each other to define one or more message series or branches. Steps 610 may correspond to different types of actions. For example, the step 610 may be sending a message 615. As another example, the step 610 may be waiting for an event 620 to occur. As yet another example, the step 610 may be a delay step to introduce a delay of a predetermined amount of time prior to proceeding with the flow. As yet another example, the step 610 may be a split step to split the group of end users of the message flow plan 600 into two or more groups for performing statistical analysis or testing (e.g., AB testing). The order of steps 610 shown in FIG. 6 is not intended to be limiting and is for illustration only. In the example shown in FIG. 6 , the message flow plan 600 defines three different message series, where the first step in each series is sending of a message, the second step in each series is a branching step based on the detail of an event, and the third step is sending off a respective message for the corresponding series. The message flow plan 600 may also be referred to as a message campaign or message automation.

The steps 610 in the message flow plan 600 may be connected in any suitable way, branched or linear, cyclic or acyclic. The transmission of an initial message (e.g., Message A) under the message flow plan 600 may be based on an associated trigger condition (e.g., target recipient criteria; publisher-configured trigger) that specifies the group of message end users to the application operator 120 that may receive messages under the message flow plan 600.

The message flow plan 600 may also set exclusion trigger conditions based on which one or more end users may be temporarily excluded or permanently removed from the group of end users and thereby prevented from receiving messages 615 under the message flow plan 600. The exclusion trigger condition may be associated with a goal of the message flow plan 600. For example, the goal of sending a series of messages to an end user under a message campaign may be to induce the end user to perform a certain action (e.g., make a purchase). The message management platform 110 may receive an event trigger from the application operator 120 when the event corresponding to the exclusion trigger condition has occurred for a given end user in the group, and the message management platform 110 may remove the given end user based on the occurrence of the exclusion trigger condition.

Subsequent messages (e.g., Messages B-D) sent under the message flow plan 600 may have corresponding trigger conditions (e.g., Trigger Conditions A-C) based on the satisfaction of which the end user of the group may receive the corresponding message. The Trigger Conditions A-C may be event-based triggers or publisher-configured triggers. In the example shown in FIG. 6 , the message flow plan 600 includes step B which is a branching step that splits end users into different branches based on details of an event (e.g., message trigger condition).

The application operator 120 may arrange the order and branching of steps 610 of the different series and compose each message 615. The application operator 120 may use the flow designer to design the payload 622, the tags 624, the opt-out notifier 626, and the conditions 628 (e.g., target recipient criteria, message trigger conditions) for triggering each message 615. The message payload 622 may include text, image content, and multimedia content such as voice, videos, and music. The tags 624 may include dynamic data (e.g., end user name) that is populated during the generation and transmission of the message 615 to a specific end user based on event payload data or end user data. The application operator 120 may also include the opt-out notifier 626 in the message 615 which may be acted upon by the end user to opt-out of or unsubscribe from receiving messages 615 from the message flow plan 600 or from the application operator. The application operator 120 may also specify the conditions 628 (e.g., message trigger conditions, target recipient criteria) for triggering a message 615 to be sent. The conditions 628 may specify that the corresponding message 615 is sent automatically or after a time delay. For example, the conditions 628 for Message A 615 may include the target recipient criteria that specify which message end users of the application operator 120 may receive the message 615. As another example, the conditions 628 for Message C may include the trigger condition B which, when met by a specific end user, causes the transmission of the message C to that end user.

Example Flow Plan Composition Process and GUI

FIG. 7 is a flowchart depicting an example process 700 for a message management platform 110 to provide an interface, e.g., message flow building platform 330, for an application operator 120 to compose and launch a flow plan 600, in accordance with some embodiments. FIG. 8A through FIG. 8E are example illustrations of graphical user interfaces provided by a message management platform 110 for an application operator 120 to compose a flow plan 600, in accordance with some embodiments. FIG. 9 is an example of a webpage 900 associated with an application operator 120 where end user activity may cause the message management platform 110 to detect a message trigger condition associated with a flow plan 600, in accordance with some embodiments. FIG. 7 is discussed in conjunction with FIG. 8A through FIG. 8E and FIG. 9 .

The message management platform 110 may cause 710 a flow designer GUI to be displayed at a publisher device of an application operator. The GUI may include a plurality of control elements for the application operator 120 to build and launch a flow plan 600. For example, the GUI may include a flow plan builder that may allow the application operator 120 to drag and drop flow actions and configure instances of the actions using action composers. The flow actions may be of different types and can be dragged and dropped into a flow outline to compose a sequence of the steps 610 of the message flow plan 600.

The message flow plan 600 may be defined by a series of rules and logic for the message management platform 110 to automatically transmit one or more messages to a plurality of target end users (target message recipients) on behalf of the application operator 120 when certain trigger conditions are met. In one embodiment, the GUI may take a form of a web browser application. In another embodiment, the GUI may take the form of a software application (e.g., a mobile application) published by the message management platform 110 and installed on a publisher device of the application operator 120 to configure the message flow plan.

The application operator 120 may build a flow plan 600 that specifies the different steps or actions for different series of messages to be automatically transmitted by the message management platform 110 in a period of time in response to corresponding conditions being met. The message management platform 110 may operate or be in communication with a GUI for the application operator 120 to build the message flow plan 600. The GUI may include a landing page, which allows the application operator 120 to input a selection to build a new flow plan 600. In response, the GUI may display a plurality of control elements (e.g., target recipient criteria, actions, action composers) that may be configured to allow the application operator 120 to build the message flow plan 600 step 610 by step 610.

Referring to FIG. 8A, the GUI may display target recipient criteria 805 that allows the application operator 120 to select the group of end users to which messages may be sent under the message flow plan 600. The target recipient criteria 805 may correspond to a message trigger condition based on which a message may be sent to end users.

The message management platform 110 may receive 720, from an application operator, a selection of message trigger condition 809 as the target recipient criteria 805 for the message flow plan 600. The message management platform 110 may further receive from an application operator 120 a selection of exclusion trigger condition 810 as the target recipient criteria 805 for the message flow plan 600.

In the example shown in FIG. 8A, all end users of the particular application operator 120 are selected as the group of end users for the message flow plan 600 as the message trigger condition 809. The target recipient criteria 805 may further include one or more exclusion trigger conditions 810 based on which one or more end users from the group selected in the target recipient criteria 805 may be excluded temporarily from receiving messages or removed permanently from the group. For example, as shown in FIG. 8A, the exclusion trigger condition 810 may specify that an end user who has created an order is to be removed from the group, thereby preventing sending further (potentially irrelevant) messages to the end user. Additional exclusion triggers 811 may be included in and as the exclusion trigger condition 810. The GUI may also include additional control elements like options to save 817 or cancel 819 changes made to the target recipient criteria 805 for the message flow plan 600, and options to save changes 820 or schedule or launch 825 the message flow plan 600 to start sending messages to end users based on the message flow plan 600.

The message management platform 110 may cause 730 the GUI to display outline 815 for the message flow plan 600 including the target recipient criteria 805 based on the selection received at block 720. That is, as shown in FIG. 8A, based on the input from the application operator 120 to set the target recipient criteria 805 (e.g., pressing the “Save” 817 button), the platform displays the outline 815 of the message flow plan 600 being configured by the publisher. The outline 815 may present the sequential steps being configured under the message flow plan 600 as a flow, so that the user can easily discern the actions being taken under the message flow plan and enable the user to easily change the message flow plan by simply dragging and dropping new instances of actions onto the outline 815, rearranging the steps of the outline 815, or editing a particular step of the outline 815 using a corresponding action composer.

To add steps or actions to the message flow plan 600, the message management platform 110 may cause 740 the GUI to display a flow composer 830 for the application operator 120 to configure steps for the message flow plan. Referring now to FIG. 8B, after the target recipient criteria 805 (including the message trigger condition 809 and any exclusion trigger conditions 810) has been saved 817, the GUI may update the outline 815 to display the saved target recipient criteria 829 in the outline 815, and further display the flow composer 830 that includes different types of actions that can be dragged and dropped into the message flow plan 600.

In the example shown in FIG. 8B, the available flow actions 830 may include an action or step to send a message 831, an action or step to introduce a delay 832 into the message flow plan 600, an action or step to add an A/B split 833, an action or step to wait for an event split 834, and an action or step to update end user 835. Actions 830 shown in FIG. 8B are illustrative only and not intended to be limiting. Additional types of actions 830 may be designed and provided by the flow designer to provide additional functionality to the application operator. The application operator 120 may easily drag and drop the actions 830 into the outline 815 and configure the added actions using a corresponding action composer to build the message flow plan 600.

For example, the application operator 120 may add the send message 831 action into the outline 815, and in response, as shown in FIG. 8C, the GUI may display the message composer 840 to configure the message to be sent to the end users. Message composer 840 may include one or more control elements 841 to enable the application operator 120 to design the message payload that is to be transmitted to the group of end users based on the message trigger conditions. The message composer 840 may further include an option 842 to enable the application operator 120 to configure opt-out settings for the message to be received by the end user, and options to save 843 or cancel 844 changes made to the message draft via the message composer 840. The message management platform 110 may cause the GUI to display a message preview 846 of the message composed using the message composer 840 in the outline 815 to visually represent the ordered sequence of steps 610 of the message flow plan 600. The message management platform 110 may further cause the GUI to display control elements 845 for the message composed using the message composer 840 in the outline 815 to enable the application operator 120 to send a preview 846 of the message to an end user computing device 140 (e.g., smartphone), duplicate the message with the configuration settings for the draft message on the outline as a next step, or delete the draft message from the message flow plan 600.

The message management platform 110 may further cause 750 the GUI to display a wait for event split composer for the application operator 120 to split end users into different branches based on details of an event trigger. The application operator 120 may drag and drop into the outline 815, the wait for event split action 834 from among the flow actions 830 shown in FIG. 8B. In response, as shown by way of example in FIG. 8D, the message management platform 110 may cause the GUI to display the wait for event composer 850 to select an event trigger condition 851 and further select event details 852 based on which the group of end users 829 of the message flow plan 600 are split into two or more branches.

The event trigger condition 851 may be selected from one or more event trigger candidates that are being tracked by the application builder platform 130 of the application operator 120 so that when a specific instance of a tracked event set as the event trigger condition 851 occurs, the message management platform 110 is notified of the instance of the event and the details (e.g., payload in key-value pairs) associated with the instance are transmitted by the application builder platform 130 to the message management platform 110 as event payload data. The one or more event trigger candidates may also include events that are being tracked directly by the message management platform 110 by embedding SDKs associated with events onto webpages hosted on the application builder platform 130 for the application operator.

A GUI may include one or more of the following event trigger candidates that can be selected as the event trigger condition 851. For example, the event trigger candidate may be a checkout started event, a customer created event, a fulfillment created event, an order created event, an order delivered event, an order fulfilled event, an order in-transit event, a product added to cart event, an end user viewed product event, a cart abandoned event, and the like. The checkout started event may be triggered when an end user on an application operator 120 storefront clicks on the checkout link after adding one or more products to a shopping cart. The customer-created event may be triggered when an order is received from a new customer. The order-created event may be triggered when a customer places an order. The product added to the cart event may be triggered when a customer adds a product to a shopping cart. The cart abandoned event may be triggered when a customer does not proceed to checkout after elapse of a predetermined period of time since adding a product to a shopping cart, or when a customer performs a predetermined action (e.g., navigating away from an online storefront) after The cart abandoned event may be triggered when a customer does not proceed to checkout after starting the checkout process but does not completing process after elapse of a predetermined period of time.

For each event trigger candidate selected as the event trigger condition 851, the message management platform 110 may receive from the application builder platform 130 of the application operator 120 an event payload including details of the instance of the triggered event. For example, for the order-created event instance, the event payload may include data (e.g., key-value pair data) customer data, product data, promotion data, activity data, and the like. More specifically, the payload may include shipping address, billing address, country code, state and province code, currency, locale, discount codes, landing site, product information, variant ID, customer ID, product ID, and the like. To split the end users into different branches, the application operator 120 may specify the event details 852 for each branch for a selected event trigger condition 851 and utilize control elements to save 854 or cancel 853 the changes made in the wait for event composer 850 of the message flow plan 600.

In the example shown in FIG. 8D, the application operator 120 has selected the Order Created event as the event trigger condition 851 and set two branches based on the billing address country code (event details 852) associated with the trigger condition 851. As shown in FIG. 8E, the message management platform 110 may cause the GUI to display a wait for event split preview 855 composed using the wait for split event composer 850 in the outline 815 to visually represent the sequence of steps of the message flow plan 600 and represent the event trigger condition 851 and event details 852 based on which the flow is to be branched into two different message series. In the example shown in FIGS. 8D and 8E, the application operator 120 has set the wait for event split such that when a new order is created and the billing address country code for the new order is the U.S., the message management platform 110 performs steps under split A 856 of the message flow plan 600, and if the billing address country code for the new order is not the U.S., the message management platform 110 performs steps under split B 857 of the message flow plan 600. Although FIGS. 8D and 8E illustrate an example where the split is between two branches, additional branches may be added based on any data point included in the event payload received from the application builder platform 130 in connection with the triggered event of the set event trigger condition 851.

Further, as shown in FIGS. 8E, the application operator 120 may add the send message 831 action into the outline 815 under split A 856 by using the message composer 840 to configure a message to be sent to the end users who meet the trigger condition associated with the wait for event split preview 855 for Split A. Similarly, as shown in FIGS. 8F, the application operator 120 may add the send message 831 action into the outline 815 under split B 857 by using the message composer 840 to configure a message to be sent to the end users who do not meet the trigger condition associated with the wait for event split preview 855 for Split A. Previews of the message drafts to be sent under the respective message series corresponding to Split A and B are shown as message preview 860 and 865 respectively in FIG. 8F. The message management platform 110 is thus configured to, for example, send different messages to end users who have placed orders with an online storefront associated with the application operator 120 to based on the end user's billing address country code.

The message management platform 110 may receive 760 a command from the application operator 120 to launch 825 the composed message flow plan. That is, after completing configuring the message flow plan 600 by using the flow designer GUI as illustrated in FIGS. 8A-8F, the application operator 120 may save changes 820 or may go ahead and schedule or launch 825 the message flow plan 600 to cause the message management platform 110 to start executing the steps 610 associated with the message flow plan and implement respective message series to different end users included in the group of end users for the message flow plan 600 based on the end users meeting different trigger conditions associated with the different message series.

At block 770, the message management platform 110 or the application builder platform 130 associated with the application operator 120 may detect the occurrence of a message trigger condition for an end user included in the group of end users for the message flow plan. For example, after the message flow plan 600 is launched, the application builder platform 130 may track the activities of visitors to one or more pages of an online storefront associated with the application operator 120 and upon the detection of an event trigger condition 851, generate the event details of the instance of the triggered event as an event payload and transmit the event payload to the message management platform 110. As another example, the message management platform 110 may embed an SDK on the application builder platform 130 to track the activities of visitors to one or more pages of the online storefront associated with the application operator 120 and upon the detection of the event trigger condition 851, generate the event details of the instance of the triggered event as the event payload.

The message management platform 110 may utilize the data in the event payload to determine whether the data corresponds to an end user included in the group of end users to the message flow plan launched at block 760 and determines the message series to implement under the message flow plan 600 based on the determination. The operations performed at block 770 are described in connection with the webpage shown in FIG. 9 .

FIG. 9 represents an e-commerce webstore page 900 of an application operator's storefront that may be hosted on the application builder platform 130. As explained previously, the application builder platform 130 may detect trigger events that are being monitored by the message management platform 110 in one or more launched flow plans and transmits the event payload when an instance of the trigger event is detected. Alternately, the SDK of the message management platform 110 may be embedded in the hosted instance of the webpage shown in FIG. 9 , which allows the message management platform 110 to track user activity on the webpage and generate the payload data based on the tracking for predetermined trigger events associated with flow plans. In the example GUI of FIG. 9 , the application operator 120 may have launched a flow plan that sends a predetermined series of messages to an end user when the end user adds a product to a cart by clicking on the button Add to Cart 905 (e.g., the message trigger condition is adding a product to cart).

Based on the action detected on the webpage 900, the message management platform 110 or the application builder platform 130 where the webpage 900 is hosted may generate event payload data associated with the instance of the add product to cart event. In the example of FIG. 9 , the payload data may include product information (e.g., shoe size, shoe color, shoe quantity), buyer information (e.g., email, phone number, billing address, shipping address), promotion information (e.g., coupons), and the like. Based on the buyer information (e.g., email, phone number, address) included in the payload, the message management platform 110 may be configured to determine whether the customer whose activity on webpage 900 has triggered the add to cart event is a registered end user of the application operator 120 (e.g., the user has previously opted-in to receive communications over SMS from the application operator). In response to determining that the user is a registered end user, the message management platform 110 may further determine whether the end user is part of the group of end users corresponding to the message flow plan 600 associated with the message trigger condition based on the target recipient criteria 805 of the message flow plan 600. In response to the message management platform 110 determining that the end user is part of the group of end users corresponding to the message flow plan 600, the message management platform 110 may implement a message series per the message flow plan 600 for the end user. That is, at block 780 in FIG. 7 , the message management platform 110 may create an instance of a message of the message flow plan 600 with respect to the end user associated with the message trigger condition.

In order to determine the product information associated with the add to cart event, the message management platform 110 may utilize the variant ID 910 associated with the webpage 900 to lookup product details like size, quantity, color, and the like. The variant ID 910 may reside in the URL of the webpage 900 or in the HTML code (not shown in figures) of the webpage 900. The identified product information may then be used by the message management platform 110 to determine which of multiple message series to implement for the end user, in case a message series in the message flow plan 600 is determined based on specifics of the product added to cart by the end user (e.g., send a first message to an end user adding a black color version of a product to a cart, and send a second different message to an end user adding a blue color version of the product to the cart). At block 790, the message management platform 110 may transmit the message to the end user based on the rules and the logic of the message flow plan 600.

Computing Machine Architecture

FIG. 10 is a block diagram illustrating components of an example computing machine that is capable of reading instructions from a computer-readable medium and execute them in a processor (or controller). A computer described herein may include a single computing machine shown in FIG. 10 , a virtual machine, a distributed computing system that includes multiples nodes of computing machines shown in FIG. 10 , or any other suitable arrangement of computing devices.

By way of example, FIG. 10 shows a diagrammatic representation of a computing machine in the example form of a computer system 1000 within which instructions 1024 (e.g., software, source code, program code, bytecode, or machine code), which may be stored in a computer-readable medium for causing the machine to perform any one or more of the processes discussed herein may be executed. In some embodiments, the computing machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.

The structure of a computing machine described in FIG. 10 may correspond to any software, hardware, or combined components shown in FIGS. 1, 2A and 3 , including but not limited to, the message management platform 110, the application builder platform 130, the user computing device 140 and various engines, interfaces, terminals, and machines shown in FIG. 3 . While FIG. 10 shows various hardware and software elements, each of the components described in FIG. 1 , FIG. 2A, and FIG. 3 may include additional or fewer elements. Further, the instructions may correspond to the functionality of components and interfaces described with FIGS. 1-9 .

By way of example, a computing machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, a smartphone, a web appliance, a network router, an internet of things (IoT) device, a switch or bridge, or any machine capable of executing instructions 1024 that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” and “computer” may also be taken to include any collection of machines that individually or jointly execute instructions 1024 to perform any one or more of the methodologies discussed herein.

The example computer system 1000 includes one or more processors 1002 such as a CPU (central processing unit), a GPU (graphics processing unit), a TPU (tensor processing unit), a DSP (digital signal processor), a system on a chip (SOC), a controller, a state machine, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or any combination of these. Parts of the computing system 1000 may also include a memory 1004 that store computer code including instructions 1024 that may cause the processors 1002 to perform certain actions when the instructions are executed, directly or indirectly by the processors 1002. Instructions can be any directions, commands, or orders that may be stored in different forms, such as equipment-readable instructions, programming instructions including source code, and other communication signals and orders. Instructions may be used in a general sense and are not limited to machine-readable codes.

One and more methods described herein improve the operation speed of the processors 1002 and reduces the space required for the memory 1004. For example, the methods described herein reduce the complexity of the computation of the processors 1002 by applying one or more novel techniques that simplify the steps in training, reaching convergence, and generating results of the processors 1002. The algorithms described herein also reduces the size of the models and datasets to reduce the storage space requirement for memory 1004.

The performance of certain of the operations may be distributed among the more than processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the one or more processors or processor-implemented modules may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the one or more processors or processor-implemented modules may be distributed across a number of geographic locations. Even though in the specification or the claims may refer some processes to be performed by a processor, this should be construed to include a joint operation of multiple distributed processors.

The computer system 1000 may include a main memory 1004, and a static memory 1006, which are configured to communicate with each other via a bus 1008. The computer system 1000 may further include a graphics display unit 1010 (e.g., a plasma display panel (PDP), a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)). The graphics display unit 1010, controlled by the processors 1002, displays a GUI (GUI) to display one or more results and data generated by the processes described herein. The computer system 1000 may also include an alphanumeric input device 1012 (e.g., a keyboard), a cursor control device 1014 (e.g., a mouse, a trackball, a joystick, a motion sensor, or another pointing instrument), a storage unit 1016 (a hard drive, a solid state drive, a hybrid drive, a memory disk, etc.), a signal generation device 1018 (e.g., a speaker), and a network interface device 1020, which also are configured to communicate via the bus 1008.

The storage unit 1016 includes a computer-readable medium 1022 on which is stored instructions 1024 embodying any one or more of the methodologies or functions described herein. The instructions 1024 may also reside, completely or at least partially, within the main memory 1004 or within the processor 1002 (e.g., within a processor's cache memory) during execution thereof by the computer system 1000, the main memory 1004 and the processor 1002 also constituting computer-readable media. The instructions 1024 may be transmitted or received over a network 1026 via the network interface device 1020.

While computer-readable medium 1022 is shown in an example embodiment to be a single medium, the term “computer-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions (e.g., instructions 1024). The computer-readable medium may include any medium that is capable of storing instructions (e.g., instructions 1024) for execution by the processors (e.g., processors 1002) and that causes the processors to perform any one or more of the methodologies disclosed herein. The computer-readable medium may include, but not be limited to, data repositories in the form of solid-state memories, optical media, and magnetic media. The computer-readable medium does not include a transitory medium such as a propagating signal or a carrier wave.

Additional Considerations

Beneficially, various embodiments described herein provide integration to application building ecosystem that allows application operators to effectively communicate with the end users of the applications while allowing the application operators to enhance the functionalities of their applications by incorporating various third-party read-to-use features. Various disclosed embodiments allow a message management platform to effectively communicate with any third-party platforms that provide features to the applications and distribute messages based on triggers that occur at the third-party platforms. This streamlines the application building process and enhance communication capability for application operators.

The foregoing description of the embodiments has been presented for the purpose of illustration; it is not intended to be exhaustive or to limit the patent rights to the precise forms disclosed. Persons skilled in the relevant art can appreciate that many modifications and variations are possible in light of the above disclosure.

Embodiments according to the invention are in particular disclosed in the attached claims directed to a method and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g. computer program product, system, storage medium, as well. The dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof is disclosed and can be claimed regardless of the dependencies chosen in the attached claims. The subject-matter which can be claimed comprises not only the combinations of features as set out in the disclosed embodiments but also any other combination of features from different embodiments. Various features mentioned in the different embodiments can be combined with explicit mentioning of such combination or arrangement in an example embodiment. Furthermore, any of the embodiments and features described or depicted herein can be claimed in a separate claim and/or in any combination with any embodiment or feature described or depicted herein or with any of the features.

Some portions of this description describe the embodiments in terms of algorithms and symbolic representations of operations on information. These operations and algorithmic descriptions, while described functionally, computationally, or logically, are understood to be implemented by computer programs or equivalent electrical circuits, microcode, or the like. Furthermore, it has also proven convenient at times, to refer to these arrangements of operations as engines, without loss of generality. The described operations and their associated engines may be embodied in software, firmware, hardware, or any combinations thereof.

Any of the steps, operations, or processes described herein may be performed or implemented with one or more hardware or software engines, alone or in combination with other devices. In some embodiments, a software engine is implemented with a computer program product comprising a computer-readable medium containing computer program code, which can be executed by a computer processor for performing any or all of the steps, operations, or processes described. The term “steps” does not mandate or imply a particular order. For example, while this disclosure may describe a process that includes multiple steps sequentially with arrows present in a flowchart, the steps in the process do not need to be performed by the specific order claimed or described in the disclosure. Some steps may be performed before others even though the other steps are claimed or described first in this disclosure.

Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein. In addition, the term “each” used in the specification and claims does not imply that every or all elements in a group need to fit the description associated with the term “each.” For example, “each member is associated with element A” does not imply that all members are associated with an element A. Instead, the term “each” only implies that a member (of some of the members), in a singular form, is associated with an element A.

Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the patent rights. It is therefore intended that the scope of the patent rights be limited not by this detailed description, but rather by any claims that issue on an application based hereon. Accordingly, the disclosure of the embodiments is intended to be illustrative, but not limiting, of the scope of the patent rights. 

The invention claimed is:
 1. A system, comprising: at least one memory; and at least one processor coupled with the at least one memory, the at least one memory storing code comprising instructions, the instructions when executed by the at least one processor cause a message management platform to perform steps comprising: presenting a user interface configured to receive, from an application operator, a configuration of a message flow, the message flow comprising recipient criteria defining a segment of subscribers to receive messages from the message flow, at least one message in the message flow associated with a trigger condition; subscribing to, on behalf of the application operator, at least one application programming interface (API) notification channel of an application builder platform, the application builder platform operational as a backend component of an application controlled by the application operator; receiving a plurality of API notifications from the application builder platform, the plurality of API notifications comprising respective API payloads that include information describing events associated with a plurality of users of the application builder platform; receiving a plurality of code-snippet notifications describing events associated with a plurality of user computing devices, a code-snippet notification being received from a user computing device of the plurality of user computing devices via a corresponding code snippet incorporated in an instance of the application operated at the user computing device, the user computing device being associated with a corresponding subscriber with a corresponding subscriber identifier used by the message management platform; identifying a plurality of user identifiers in the plurality of API payloads from the application builder platform; determining that the plurality of user identifiers in the plurality of API payloads correspond to a plurality of subscriber identifiers used by the message management platform; storing, for a first subscriber associated with a first subscriber identifier, subscriber events, the subscriber events comprising one or more events described in one or more API notifications associated with the first subscriber and one or more events described in one or more code-snippet notifications from one of the user computing devices associated with the first subscriber identifier; determining, based on a plurality of the stored subscriber events associated with the first subscriber, that the first subscriber satisfies the recipient criteria; enrolling the first subscriber to the segment of subscribers who are to receive messages from the message flow in response to the determination that the recipient criteria is satisfied; monitoring the trigger condition in the message flow in response to the first subscriber being enrolled in the segment of subscribers; receiving one or more new subscriber events associated with the first subscriber; determining that the one or more new subscriber events meet the trigger condition in the message flow; and transmitting the at least one message in the message flow that is associated with the trigger condition to the first subscriber.
 2. The system of claim 1, wherein the user interface is part of a message flow builder that allows the application operator to build the message flow.
 3. The system of claim 1, wherein the corresponding code snippet is listed in a digital distribution platform of the application builder platform.
 4. The system of claim 1, wherein each API payload comprises a plurality of key-value pairs, the plurality of key-value pairs comprising a user identifier used by the application builder platform and a phone number of a user of the application builder platform.
 5. The system of claim 1, wherein the instructions when executed by the one or more processors further causes the message management platform to perform steps comprising: generating, responsive to receiving a code-snippet notification indicating that the one of the user computing devices has used the application, a random string that is used as at least a part of the first subscriber identifier; generating a cookie based on the random string; and transmitting the cookie to the one of the user computing devices.
 6. The system of claim 1, wherein a subscriber event described in an API notification received from the application builder platform is related to a transaction performed at the backend component that is operated by the application builder platform.
 7. The system of claim 1, wherein the at least one message in the message flow is transmitted to the first subscriber in response to determining that the one or more new subscriber events meet the trigger condition.
 8. The system of claim 1, wherein the first subscriber is automatically enrolled to the segment of subscribers that receive messages from the message flow in response to determining that the first subscriber satisfies the recipient criteria for the message flow.
 9. The system of claim 1, further comprising instructions that cause the message management platform to perform a step comprising: introducing, after enrolling the first subscriber to the segment of subscribers who are to receive messages from the message flow, a delay of a predetermined amount of time prior to proceeding with the message flow.
 10. The system of claim 1, wherein the plurality of the stored subscriber events associated with the first subscriber based on which the first subscriber is determined to satisfy the recipient criteria for the message flow include events described in a plurality of API notifications associated with the first subscriber.
 11. A computer-implemented method, comprising: receiving, from an application operator, a configuration of a message flow, the message flow comprising recipient criteria defining a segment of subscribers to receive messages from the message flow, at least one message in the message flow associated with a trigger condition; subscribing to, on behalf of the application operator, at least one application programming interface (API) notification channel of an application builder platform, the application builder platform operational as a backend component of an application controlled by the application operator; receiving a plurality of API notifications from the application builder platform, the plurality of API notifications comprising respective API payloads that include information describing events associated with a plurality of users of the application builder platform; receiving a plurality of code-snippet notifications describing events associated with a plurality of user computing devices, a code-snippet notification being received from a user computing device of the plurality of user computing devices via a corresponding code snippet incorporated in an instance of the application operated at the user computing device, the user computing device being associated with a corresponding subscriber with a corresponding subscriber identifier used by a message management platform; identifying a plurality of user identifiers in the plurality of API payloads from the application builder platform; determining that the plurality of user identifiers in the plurality of API payloads correspond to a plurality of subscriber identifiers used by the message management platform; storing, for a first subscriber associated with a first subscriber identifier, subscriber events, the subscriber events comprising one or more events described in one or more API notifications associated with the first subscriber and one or more events described in one or more code-snippet notifications from one of the user computing devices associated with the first subscriber identifier; determining, based on a plurality of the stored subscriber events associated with the first subscriber, that the first subscriber satisfies the recipient criteria; enrolling the first subscriber to the segment of subscribers who are to receive messages from the message flow in response to the determination that the recipient criteria is satisfied; monitoring the trigger condition in the message flow in response to the first subscriber being enrolled in the segment of subscribers; receiving one or more new subscriber events associated with the first subscriber; determining that the one or more new subscriber events meet the trigger condition in the message flow; and transmitting the at least one message in the message flow that is associated with the trigger condition to the first subscriber.
 12. The computer-implemented method of claim 11, wherein the configuration is received through a user interface that allows the application operator to build the message flow.
 13. The computer-implemented method of claim 11, wherein the corresponding code snippet is listed in a digital distribution platform of the application builder platform.
 14. The computer-implemented method of claim 11, wherein each of the plurality of API notifications is a webhook notification.
 15. The computer-implemented method of claim 11, wherein each API payload comprises a plurality of key-value pairs, the plurality of key-value pairs comprising a user identifier used by the application builder platform and a phone number of a user of the application builder platform.
 16. The computer-implemented method of claim 11, further comprising: generating, responsive to receiving a code-snippet notification indicating that the one of the user computing devices has used the application, a random string that is used as at least a part of the first subscriber identifier; generating a cookie based on the random string; and transmitting the cookie to the one of the user computing devices.
 17. The computer-implemented method of claim 11, wherein a subscriber event described in an API notification received from the application builder platform is related to a transaction performed at the backend component that is operated by the application builder platform.
 18. The computer-implemented method of claim 11, wherein the first subscriber is automatically enrolled to the segment of subscribers that receive messages from the message flow in response to determining that the first subscriber satisfies the recipient criteria for the message flow.
 19. The computer-implemented method of claim 11, further comprising: introducing, after enrolling the first subscriber to the segment of subscribers who are to receive messages from the message flow, a delay of a predetermined amount of time prior to proceeding with the message flow.
 20. The computer-implemented method of claim 11, wherein the plurality of the stored subscriber events associated with the first subscriber based on which the first subscriber is determined to satisfy the recipient criteria for the message flow include events described in a plurality of API notifications associated with the first subscriber.
 21. A system, comprising: a code snippet incorporated in an application of a user computing device, wherein the application is controlled by an application operator and has a backend component that is operated by an application builder platform; and a message management platform comprising one or more processors and memory, the memory configured to store code comprising instructions, wherein the instructions, when executed by the one or more processors, cause the one or more processors to perform steps comprising: receiving, from the application operator, a configuration of a message flow, the message flow comprising recipient criteria defining a segment of subscribers to receive messages from the message flow, at least one message in the message flow associated with a trigger condition; subscribing to, on behalf of the application operator, at least one application programming interface (API) notification channel of the application builder platform; receiving a plurality of API notifications from the application builder platform, the plurality of API notifications comprising respective API payloads that include information describing events associated with a plurality of users of the application builder platform; receiving a plurality of code-snippet notifications describing events associated with a plurality of user computing devices, a code-snippet notification being received from the user computing device of the plurality of user computing devices via the code snippet incorporated in the application of the user computing device, the user computing device being associated with a corresponding subscriber with a corresponding subscriber identifier used by the message management platform; identifying a plurality of user identifiers in the plurality of API payloads from the application builder platform; determining that the plurality of user identifiers in the plurality of API payloads correspond to a plurality of subscriber identifiers used by the message management platform; storing, for a first subscriber associated with a first subscriber identifier, subscriber events, the subscriber events comprising one or more events described in one or more API notifications associated with the first subscriber and one or more events described in one or more code-snippet notifications from one of the user computing devices associated with the first subscriber identifier; determining, based on a plurality of the stored subscriber events associated with the first subscriber, that the first subscriber satisfies the recipient criteria; enrolling the first subscriber to the segment of subscribers who are to receive messages from the message flow in response to the determination that the recipient criteria is satisfied; monitoring the trigger condition in the message flow in response to the first subscriber being enrolled in the segment of subscribers; receiving one or more new subscriber events associated with the first subscriber; determining that the one or more new subscriber events meet the trigger condition in the message flow; and transmitting the at least one message in the message flow that is associated with the trigger condition to the first subscriber.
 22. The system of claim 21, further comprising a user interface that is part of a message flow builder that allows the application operator to build the message flow.
 23. The system of claim 21, wherein the code snippet is listed in a digital distribution platform of the application builder platform.
 24. The system of claim 21, wherein each of the plurality of API notifications is a webhook notification.
 25. The system of claim 21, wherein each API payload comprises a plurality of key-value pairs, the plurality of key-value pairs comprising a user identifier used by the application builder platform and a phone number of a user of the application builder platform.
 26. The system of claim 21, wherein the instructions, when executed by the one or more processors, cause the one or more processors to perform: generating, responsive to receiving a code-snippet notification indicating that the one of the user computing devices has used the application, a random string that is used as at least a part of the first subscriber identifier; generating a cookie based on the random string; and transmitting the cookie to the one of the user computing devices.
 27. The system of claim 21, wherein a subscriber event described in an API notification received from the application builder platform is related to a transaction performed at the backend component that is operated by the application builder platform.
 28. The system of claim 21, wherein the first subscriber is automatically enrolled to the segment of subscribers that receive messages from the message flow in response to determining that the first subscriber satisfies the recipient criteria for the message flow.
 29. The system of claim 21, further comprising instructions that cause the message management platform to perform a step comprising: introducing, after enrolling the first subscriber to the segment of subscribers who are to receive messages from the message flow, a delay of a predetermined amount of time prior to proceeding with the message flow.
 30. The system of claim 21, wherein the plurality of the stored subscriber events associated with the first subscriber based on which the first subscriber is determined to satisfy the recipient criteria for the message flow include events described in a plurality of API notifications associated with the first subscriber. 